home *** CD-ROM | disk | FTP | other *** search
Text File | 1994-06-27 | 1.5 KB | 51 lines | [TEXT/MPS ] |
- The tokenizer is implemented as a CForth-93 dictionary. To use the tokenizer,
- execute the CForth-93 tool, specifying the dictionary as follows:
-
- CForth93 tokenizer.dic
-
- This will load the CForth93 tool, which will, in turn, load the tokenizer's dictionary.
- At this point, the tokenizer is awaiting a command. (Unfortunately, due to the cruddy
- manner in which terminal I/O is simulated in MPW, no prompt is supplied. The flashing
- cursor is the only indication that the tokenizer is waiting.)
-
- To tokenize a file, type:
-
- tokenize <filename>
-
- This will start tokenizing the top-level file. Within this file, a tokenizer FLOAD
- command can be used to include other files. This command looks like:
-
- fload <filename>
-
- FLOADs can be nested.
-
- The tokenizer builds the FCode image into an internal buffer. After all the source
- has been tokenized, the image is saved by using the save-image command as:
-
- save-image <filename>
-
- Then, type
-
- bye
-
- to exit CForth93.
-
- In addition to the standard Open Firmware words, two additional words have been added
- to make it easier to produce PCI Expansion ROM images. These are:
-
- pci-header
- pci-end
-
- They should bracket the normal Open Firmware code. The pci-header command will generate
- a PCI image header first. So, a complete FCode image will be generated by:
-
- pci-header \ generate proper PCI image header
- version1 \ generate proper FCode header (within PCI image)
- ...
- ...
- end0 \ terminate normal FCode
- pci-end \ complete the PCI image
-
-
-
-